Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add create shcmea for sqlalchemy datastore #965

Merged
merged 3 commits into from
Sep 22, 2024
Merged

Conversation

zhu0629
Copy link
Contributor

@zhu0629 zhu0629 commented Sep 18, 2024

Changes

Add create shcmea for sqlalchemy datastore

Fixes #.

Checklist

If this is a user-facing code change, like a bugfix or a new feature, please ensure that
you've fulfilled the following conditions (where applicable):

  • [ ] You've added tests (in tests/) added which would fail without your patch
  • [ ] You've updated the documentation (in docs/, in case of behavior changes or new
    features)
  • [ x ] You've added a new changelog entry (in docs/versionhistory.rst).

If this is a trivial change, like a typo fix or a code reformatting, then you can ignore
these instructions.

Updating the changelog

If there are no entries after the last release, use **UNRELEASED** as the version.
If, say, your patch fixes issue #999, the entry should look like this:

* Fix big bad boo-boo in the async scheduler (#999 <https://github.com/agronholm/apscheduler/issues/999>_; PR by @yourgithubaccount)

If there's no issue linked, just link to your pull request instead by updating the
changelog after you've created the PR.

@coveralls
Copy link

coveralls commented Sep 18, 2024

Coverage Status

coverage: 92.033% (-0.05%) from 92.08%
when pulling c44876e on zhu0629:dev
into 0bcb319 on agronholm:master.

@agronholm
Copy link
Owner

You checked the boxes for having updated the documentation and added a changelog. Can you point out to me where you've done this?

@agronholm
Copy link
Owner

Please don't add unrelated changes to this PR.

@agronholm
Copy link
Owner

I will make the necessary updates in master and you can then merge them here. I'll let you know when it's done.

@agronholm
Copy link
Owner

I've updated master now, and you can rebase your work against that.

docs/versionhistory.rst Outdated Show resolved Hide resolved
src/apscheduler/datastores/sqlalchemy.py Outdated Show resolved Hide resolved
src/apscheduler/datastores/sqlalchemy.py Outdated Show resolved Hide resolved
@agronholm
Copy link
Owner

Please merge from master because your force pushes are now undoing the updates I made.

@agronholm
Copy link
Owner

Could you please stop force-pushing your changes? It's causing some previous updates from master from being undone. There's no reason to do that, as I will squash the changes when merging anyway.

@agronholm agronholm merged commit d4d0670 into agronholm:master Sep 22, 2024
14 checks passed
@agronholm
Copy link
Owner

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants